Add 3rd party tests for litestar#578
Conversation
There was a problem hiding this comment.
These tests are nice and fast, the 3rd-party CI only runs once a night, and litestar is a very popular library -- so this seems pretty reasonable to me!
Each new library we add to this workflow adds a certain maintenance burden for us, as they do fail reasonably often due to changes beyond our control. I think this one meets the cost-benefit threshhold for it to be worth it, though.
FYI: we also publish release candidates for every |
Thanks for the pointer, I've added a workflow to test against typing-extension pre-releases on our side as well :) |
|
All commit authors signed the Contributor License Agreement. |
3 participants
Add Litestar to the 3rd party tests.
The package relies significantly on runtime type inspections (and therefore
typing-extensions🙂), and we've been made aware that it was also affected by #560.The issue had first been raised as a Debian bug report and was forwarded to us; An early(er) warning could have been useful to avoid this downstream issue.
The tests themselves don't take too long (~30-60 seconds), as we only need to run a subset of our test suite.